I think a discussion of the security risks needs to be up-front in the debugging guide. It might be possible have a summary section and link to a detailed document elsewhere. Let me take a look at refactoring.

@marswong I took a deeper look at refactoring this PR into two document, and I don't think there is a refactor into two documents that would be satisfactory:

• We need to make people aware that there are security implications. These should be in the primary debugging guide.
• The details about how to do remote debugging must also be in the primary debugging guide. Those are instructions.
• The only thing that can be split out is the nature of the security issues. I tried extracting these into a standalone doc, but I wasn't satisfied with the result because the security doc has to refer back to the guide on how to enable remote debugging in light of the security issues.

In summary, I think we should keep this a single doc. Even though this doc is called the 'Debugging Getting Started' guide, in reality it is actually the 'Debugging Guide'. I think security implications should stay in this doc.

I would like to land this as-is. WDYT?

@ofrobots Can you please fix the little nits @vsemozhetbyt mentioned, and I think we are good to go. If we feel the need to restructure the document, we can do so at a later point.

Thank you!

@ofrobots good job :)